Skip to main content
Feedback

Call Transformations

The Call Transformation feature enables Boomi Cloud API Management endpoints to plug in pre-processors and post-processors (Boomi Cloud API Management Connectors).

The Traffic Manager can apply processing logic to an API request before it is sent to the host API servers and after the response is returned from the client API servers. A typical use case for processing logic is protocol translation.

For example, when a developer makes an XML-RPC call to the client API servers that require REST-based API requests, the Traffic Manager translates the request to REST using specific translation logic. Protocol translation can make the API appear more robust by supporting multiple protocols when, in fact, it only supports a single protocol. Other common use cases for the processing adapter include content injection, filtering, and transformation.

important

  • The Call Transformations tab is only available when the feature flag is enabled for your area in Cloud API Management. Once enabled, the feature flag cannot be disabled.

  • ASR (Application Service Registry) services set up in Boomi Cloud will only be available in ASR Picker if they are marked Private. The Services defined for Post methods with no variable set on the path can only be successfully selected on the Call Transformation page. This means that query parameters cannot be added, and none of the endpoint's path values can be dynamically populated at runtime.

The Call Transformations page for an endpoint includes the following fields:

Processing Adapter

This field is used to specify the class file of custom logic that the Traffic Manager uses to perform pre-processing or post-processing of an API call.

Perform Pre-processing

This field configures the Traffic Manager to process the API request before it is sent to the client API server. When enabled, the Traffic Manager applies custom processing logic to an API call before the sending the request to the client API servers.

Data to make available for pre-processing

This field configures the Traffic Manager to add new values or modify the existing values within the incoming API call before passing it to the client API servers.

Perform Post-processing

This field configures the Traffic Manager to process the API call before it is sent to the client API server. When enabled, the Traffic Manager applies custom processing logic to responses from the client API servers.

Data to make available for post-processing

This field configures the Traffic Manager to add new values or modify the existing values within the incoming API call before passing it to the client API servers.

Next Steps

Configure Call Transformation for an endpoint. Refer to Configuring Call Transformation for an Endpoint for more information on the configuration steps.

On this Page